DON'T MERGE: add job posting rules to the member handbook #6

rebeccaskinner · 2018-05-24T22:51:00Z

No description provided.

beccastevens · 2018-05-24T23:07:56Z

content/member-handbook.md

+
+The STL Tech Slack is concerned with helping people who are in St. Louis find
+jobs.  To that extent, we ask that all jobs that are posted be jobs that can be
+carried out by people in St. Louis.  This means local on-sight, local remote,


I believe the correct term in this context is: on-site

+1 for on-site.

beccastevens · 2018-05-24T23:17:24Z

content/member-handbook.md

+aggregate job postings must also disclose that the poster is an external
+recruiter, as well as the type(s) of roles that are avilable (contract, direct
+hire, contract to hire).  Additionally, for anyone posting aggregate listings,
+we ask that the job post be available via the STL Tech Slack to answer any


job poster?

beccastevens · 2018-05-24T23:17:45Z

content/member-handbook.md

+recruiter, as well as the type(s) of roles that are avilable (contract, direct
+hire, contract to hire).  Additionally, for anyone posting aggregate listings,
+we ask that the job post be available via the STL Tech Slack to answer any
+questions.  Any postings aggregate postings that are answered with a requirement


postings is here twice

Hellmark · 2018-05-25T01:05:09Z

content/member-handbook.md

+to For Hire postings.  They should be short, inclusive of the types of work
+available, and limited to being posted weekly.  For external recruiters,
+aggregate job postings must also disclose that the poster is an external
+recruiter, as well as the type(s) of roles that are avilable (contract, direct


Typo here. "Avilable"

Hellmark · 2018-05-25T01:48:45Z

content/member-handbook.md

+    rough geographic area of the work site. Examples would include:
+    "Chesterfield", "Near Forest Park" or "At T-Rex".
+  - Your Relationship to the Role: Job postings MUST disclose the relationship
+    of the post to the company or role.  This includes explicity diclosure if


Explicity? Shouldn't it be explicit?

thetristan · 2018-05-25T02:02:20Z

content/member-handbook.md

+The STL Tech Slack is concerned with helping people who are in St. Louis find
+jobs.  To that extent, we ask that all jobs that are posted be jobs that can be
+carried out by people in St. Louis.  This means local on-sight, local remote,
+and full-time remote jobs are all okay.  There are no strict geographical bounds


What's the difference between local remote vs full-time remote?

I was using "local remote" for things where the company is in St. Louis and you can commute to the office, but can typically work from home. I'll add a clarification

thetristan · 2018-05-25T02:03:51Z

content/member-handbook.md

+  - Participate in the community, don't just stop by to dump a job listing and
+    then go silent.
+
+


Do you think we could loop in some of the folks actively engaged in hiring (recruiters or otherwise) to collaborate on an example of what a good posting looks like so we can share that here?

�As much as we pay lip service to some of the recruiters not being total dumpster fires, I've not really seen good postings coming from them.

In my experience, you start noticing the lack of dumpster fireness when you start working with them. The posts themselves still kinda suck.

Lisa explained this well: when she's recruiting, she's often not recruiting for a single job but multiple. Plus, she'll recommend applying different places after talking with someone. So is the solution a job board? 🤷‍♂️

I was hoping to cover that use case with the big on aggregate job postings, but we could clarify it more if necessary I guess

I don't think it's appropriate to list margins within the job postings. That's something that a good recruiter would share once speaking with the individual.

BrianHicks · 2018-05-25T18:58:08Z

content/member-handbook.md

+
+Pinned messages more than 90 days old will be periodically cleared out by
+administrators.  If you have fulfilled the pinned request (filled the role,
+gotten a job) then we would request that you unpin the message yourself.


🔀 "please unpin the message yourself."

BrianHicks · 2018-05-25T18:58:46Z

content/member-handbook.md

+administrators.  If you have fulfilled the pinned request (filled the role,
+gotten a job) then we would request that you unpin the message yourself.
+
+#### Pinned Message Eligiability


Eligibility

BrianHicks · 2018-05-25T18:59:48Z

content/member-handbook.md

+the current one.  No hard restrictions are placed on how often you may unpin old
+posts and re-pin new ones, although moderators may request that you reduce
+the frequency of pinning our our discression if it appears to be interfering
+with the normal functioning of the `#jobs` channel.


Better to make a guideline. How about not posting the same job more often than every two weeks?

(also: "discretion")

BrianHicks · 2018-05-25T19:00:18Z

content/member-handbook.md

+
+### Pinning Posting Durations
+
+#### About Pinning


pinning is like the least important part of all of this. It should go at the end.

BrianHicks · 2018-05-25T19:01:31Z

content/member-handbook.md

+
+In order to encourage maximum transparency in our job postings, we place more
+stringent requirements for pinned job postings than unpinned postings.
+Aggregate job listings are not eligible for pinning.  Furthermore, a pinned job


The talk about "eligibility" makes this all sound very formal, when this is really just setting some expectations around a loose community practice that already exists. The tone could be more peer-to-peer than grantor-to-grantee.

BrianHicks · 2018-05-25T19:02:38Z

content/member-handbook.md

+least 3 of the 6 recommended fields.
+
+For-hire postings are always eligible for pinning as long as the person seeking
+employment is a member in good standing of the community.


this paragraph should move to the next section.

BrianHicks · 2018-05-25T19:03:15Z

content/member-handbook.md

+### When You're Looking for Work
+
+The `#jobs` channel is available for anyone to use if they are looking for
+technical work.  If you're looking for work, feel free to post a link to your


only technical? What about PMs, designers, DBAs, QA people? Students and teachers?

Yeah, I do agree here, only thing is finding the right wording for the whole umbrella. It isn't all just IT, or dev, or design. Lots of different loosely related roles.

"tech related work". is the best I can come up with so far.

BrianHicks · 2018-05-25T19:09:16Z

content/member-handbook.md

+posting, but we encourage members of the STL Tech community go personalize the
+message for the audience.  In particular:
+
+  - Leverage tools like [joblint](http://joblint.org) to ensure your job posting


"leverage"… how about "use"?

BrianHicks · 2018-05-25T19:09:30Z

content/member-handbook.md

+
+  - Leverage tools like [joblint](http://joblint.org) to ensure your job posting
+    does not contain language that would exclude marginalized people.
+  - Avoid terms like "rockstar" and "ninja".


this is covered in joblint, isn't it?

It does, but further iteration, so people are totally clear. Plus Joblint sometimes misses some things you'd really expect to get covered.

BrianHicks · 2018-05-25T19:11:31Z

content/member-handbook.md

+hire, contract to hire).  Additionally, for anyone posting aggregate listings,
+we ask that the job poster be available via the STL Tech Slack to answer any
+questions.  Anyone creating  aggregate postings then responding to questions
+with a request for a phonecall / email will be banned.


This is a little harsh. This is not an one-and-done bannable thing. People tend to learn what's acceptable over time. If someone does it once, warn them. If they do it again, a ban is fine. But this is a longish document with a few cliffs to fall off already.

I'd suggest tweaking to "may be banned" or "may be punished, up to and including banning" or something like that.

add job posting rules to the member handbook

4f73e28

beccastevens reviewed May 24, 2018

View reviewed changes

Hellmark reviewed May 25, 2018

View reviewed changes

thetristan reviewed May 25, 2018

View reviewed changes

rebeccaskinner added 2 commits May 25, 2018 13:14

fix some spelling and grammar errors, and add a section on pinning

a94c210

spelling

6971616

BrianHicks reviewed May 25, 2018

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

DON'T MERGE: add job posting rules to the member handbook #6

DON'T MERGE: add job posting rules to the member handbook #6

rebeccaskinner commented May 24, 2018

beccastevens May 24, 2018

Hellmark May 25, 2018

beccastevens May 24, 2018

beccastevens May 24, 2018

Hellmark May 25, 2018

Hellmark May 25, 2018

thetristan May 25, 2018

rebeccaskinner May 25, 2018

thetristan May 25, 2018

rebeccaskinner May 25, 2018

Hellmark May 25, 2018

BrianHicks May 25, 2018

rebeccaskinner May 25, 2018

booch May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

Hellmark May 29, 2018

BrianHicks May 25, 2018

BrianHicks May 25, 2018

Hellmark May 29, 2018

BrianHicks May 25, 2018

Hellmark May 29, 2018

		- Participate in the community, don't just stop by to dump a job listing and
		then go silent.

DON'T MERGE: add job posting rules to the member handbook #6

Are you sure you want to change the base?

DON'T MERGE: add job posting rules to the member handbook #6

Conversation

rebeccaskinner commented May 24, 2018

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment